-
-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Rk 6.1 to rkr4.1 #289
Update Rk 6.1 to rkr4.1 #289
Conversation
Signed-off-by: Ken Wang <[email protected]>
Signed-off-by: Ken Wang <[email protected]>
Signed-off-by: Ken Wang <[email protected]>
…QUEST_FW" This reverts commit 1659a56.
- taken from https://github.com/hardkernel/linux/tree/odroidm1-4.19.y sha1 89b88ec44cb98ec17b8460cc3c0127fcb1f7b159 - added the infamous delete chosen - moved stuff HK did to common rk3568-linux.dtsi to their own dtsi - change `RK_GPIO0` -> `0`
- suggested by amazingfate - from way back in February; armbian/build#4794 (comment)
…#285) * add overlay:armsom-w3-camera-ov13850-csi * fix : armsom-w3 screen and camera loading method * add armsom-w3 overlay/Makefile * fix: add armsom-w3 overlay/makefile --------- Co-authored-by: [email protected] <yidiantongxin>
This is required for drivers/gpu/drm/rockchip/rockchip_drm_logo.c to compile properly as a module. Without this patch, build including rockchip-drm fail for me with ERROR: modpost: "memblock_free" undefined! cherry-picked from https://android.googlesource.com/kernel/common/+/cd5f5cb9fe677466551e44039b31198e7b0dc812%5E%21/
…g features Follow sdk commit: "dt-bindings: display: drm_mipi_dsi: Add _NO_ to MIPI_DSI_* flags disabling features"
Tested jammy with panfork driver, although DDK is bumped to g25p0, panfork can still use mali firmware from g15p0. |
On that note, do keep in mind that there's a new flag |
That is far better than the old way! |
@JeffyCN can you update the libmali mirror with the g25p0 userspace driver? |
AFAIK there is no g25 userspace driver available... |
updated to the newest version :) |
I've been experiencing a kernel panic on boot on an Radxa CM5 with this branch. I'm using a custom kernel config though, as well as a custom carrier board. The custom config fully worked on 6.1-rkr3. I'll check if I can reproduce the issue with the official carrier board soon, just wanted to let you know that there could be an issue with this branch. |
FWIW, this kernel boots perfectly fine on my CM5 with the Radxa I/O board. |
what kind if kernel panic, are there logs of it? |
Just checked again: It was related to undervoltage 😅 Using a different power supply fixed it, apparently mine was faulty. |
Tested with:
|
Gonna test on these later
Both confirmed working with rkr4.1 |
Dropped commits:
lets see if it will break panfork